Repository navigation
Fix: activate CLI plan mode only through /plan - #115
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regular CLI requests could unexpectedly enter structured plan approval because of complexity detection or a model-generated plan proposal. Now users explicitly choose that workflow with
/plan; ordinary requests, including multi-step work and prose outlines, run through the normal agent flow.The CLI no longer runs its automatic planning heuristic and excludes
propose_planfrom normal model tools. Its instructions explain the explicit behavior, and the restriction survives model/config/tool rebuilds. Explicit plan generation, review, editing, execution, and recovery remain available. Desktop retains its current planning behavior.Changelog and CLI guide updated. Local launch settings excluded.
Validation